Allow py313 to be a third Python build #156
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR undoes my recent PRs #154 and #155. My goal was to reduce the CI resources by only building two versions of Python instead of 3. However, trying to manually build only py39 and py313 has proved challenging, and I've determined it's not worth the effort to continue troubleshooting. Once the py313 conda-forge migration has finished, then I'll update this repo.
xref: #151 (comment)
Example run that demonstrates that only the CI files for py310 and py311 are deleted: https://github.com/TileDB-Inc/conda-forge-nightly-controller/actions/runs/12164471665/job/33926203028#step:15:31